home *** CD-ROM | disk | FTP | other *** search
- Path: newsbf02.news.aol.com!not-for-mail
- From: dogmat@aol.com (Dogmat)
- Newsgroups: comp.lang.java,comp.lang.c++,comp.lang.smalltalk
- Subject: Re: Will Java kill C++?
- Date: 19 Apr 1996 19:52:51 -0400
- Organization: America Online, Inc. (1-800-827-6364)
- Sender: root@newsbf02.news.aol.com
- Message-ID: <4l990j$c7p@newsbf02.news.aol.com>
- References: <3177B2BC.482B@dmu.ac.uk>
- Reply-To: dogmat@aol.com (Dogmat)
- NNTP-Posting-Host: newsbf02.mail.aol.com
-
- "Alan L. Lovejoy" <alovejoy@concentric.net> wrote
-
- >Self stores methods in slots of the object itself--directly mapping
- >an object to its behavior. Smalltalk stores methods in the class...
-
- Anyone agree with me that the Self approach is conceptually superior?
- Note: I am not interested in the pros and cons of the implementation or
- the syntax, or the difficulties of managing it, or the dangers of its
- abuse. What I am suggesting is, at the conceptual level (i.e., the long
- term view), the bottom line is: One of the two is limiting, the other is
- not. In Smalltalk, an instance is locked in (unless you go to great
- lengths to get around it, and the results can be tragic). In Self, an
- instance is free to evolve.
-